Skip to content

Set super_read_only off during restore; achieves same as PR #8929#9240

Merged
askdba merged 2 commits intovitessio:mainfrom
planetscale:jg_super_readonly
Nov 24, 2021
Merged

Set super_read_only off during restore; achieves same as PR #8929#9240
askdba merged 2 commits intovitessio:mainfrom
planetscale:jg_super_readonly

Conversation

@aquarapid
Copy link
Copy Markdown
Contributor

In short, we are blindly setting super_read_only off in the restore flow, in case the default my.cnf params has super_read_only=ON. This allows us to populate our metadata tables without running into write issues.

Tested manually and by the current DB restore e2e flow.

…8929

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
@aquarapid aquarapid added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Backup and Restore release notes labels Nov 15, 2021
@aquarapid aquarapid requested a review from deepthi as a code owner November 15, 2021 23:21
will fail.

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
@aquarapid
Copy link
Copy Markdown
Contributor Author

Ah nevermind; converting to SQLError won't work as you noted. I'll leave this as-is for now.

@askdba askdba merged commit 534c429 into vitessio:main Nov 24, 2021
@askdba askdba deleted the jg_super_readonly branch November 24, 2021 09:44
@deepthi deepthi mentioned this pull request Dec 1, 2021
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: Backup and Restore Type: Enhancement Logical improvement (somewhere between a bug and feature)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants